Modular systems and methods for selectively enabling cloud-based assistive technologies

ABSTRACT

Methods and systems for manual and programmatic remediation of websites. JavaScript code is accessed by a user device and optionally calls TTS, ASR, and RADAE modules from a remote server to thereby facilitate website navigation by people with diverse abilities.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.16/430,210, filed Jun. 3, 2019, and titled “MODULAR SYSTEMS AND METHODSFOR SELECTIVELY ENABLING CLOUD-BASED ASSISTIVE TECHNOLOGIES,” which is acontinuation of U.S. patent application Ser. No. 15/074,818, filed Mar.18, 2016, now U.S. Pat. No. 10,444,934, and titled “MODULAR SYSTEMS ANDMETHODS FOR SELECTIVELY ENABLING CLOUD-BASED ASSISTIVE TECHNOLOGIES.”Each of the foregoing applications is hereby incorporated by referencein its entirety. This application relates to U.S. patent applicationSer. No. 16/533,568, filed Aug. 6, 2019, and titled “SYSTEMS, DEVICES,AND METHODS FOR FACILITATING WEBSITE REMEDIATION AND PROMOTING ASSISTIVETECHNOLOGIES,” which is a continuation of U.S. patent application Ser.No. 15/999,116, filed Aug. 16, 2018, now U.S. Pat. No. 10,423,709, andtitled “SYSTEMS, DEVICES, AND METHODS FOR AUTOMATED AND PROGRAMMATICCREATION AND DEPLOYMENT OF REMEDIATIONS TO NON-COMPLIANT WEB PAGES ORUSER INTERFACES.”

TECHNICAL FIELD

The present invention relates, generally, to systems and methods forselectively enabling cloud-based assistive technologies and, moreparticularly, to techniques for remediating websites and other graphicaluser interfaces to enhance the user experience for people with diverseabilities, in particular aging populations and individuals who havevision, hearing, motor, and intellectual disabilities, including thosewho are color blind, dyslexic, learning to read, and looking to maintainfocus, or multi-task.

BACKGROUND

Screen reader software applications, or simply “screen readers,”translate textual and graphical information displayed on a screen andre-present it to the user using synthesized speech, sound icons, and/ora refreshable Braille output device. Screen readers are a form ofassistive technology (AT) potentially useful to the blind, visuallyimpaired, color blind, low vision, dyslexic, illiterate or learningdisabled, often in combination with other ATs such as screen magnifiersand tools for manipulating font type, font size, contrast, and the like.

Native screen readers include the Microsoft Narrator™ for Windowsoperating systems, Apple's VoiceOver™ for Mac OS X and iOS, and Google'sTalkBack™ for Android operating systems. The console-based Oralux Linuxships with three console screen-reading environments: Emacspeak™, Yasr™,and Speakup™. Popular free and open source screen readers include theOrca™ for Unix-like systems and NonVisual Desktop Access (NVDA™) forWindows.

Other screen readers are packaged as separate commercial products suchas JAWS™ (Job Access With Speech) from Freedom Scientific, Window-Eyes™from GW Micro, Dolphin Supernova™ by Dolphin, System Access™ fromSerotek, and ZoomText™ Magnifier/Reader from AiSquared.

The ReadSpeaker™ text-to-speech conversion tool available atReadSpeaker.com speaks website text aloud, but does not allow the userto jump ahead, navigate thru, or otherwise interact with the site.Rather, the user experience is analogous to using a Kindle™ augmentedwith a screen reader, where the user is a passive listener. Brousealoud™by texthelp.com and SiteCues by aiSquared allow the user to dynamicallyre-direct focus to the cursor while playing synthesized speech.

Presently known screen readers are limited, however, in that they do nothave the ability to remediate sites which do not comply with industryrecognized best practices, such as the Web Content AccessibilityGuidelines (WCAG) 2.0, Accessible Rich Internet Applications (WAI-ARIA),Authoring Tool Accessibility Guidelines (ATAG), Section 508 Standards &Technical Requirements, and other existing and forthcoming national andinternational standards and guidelines such as those resources madeavailable at https://www.w3.org/standards/webdesign/accessibility. Inparticular, the WCAG guidelines variously contemplate, inter alia,descriptive headings/labels (WCAG 2.4.6), proper form input labels (WCAG1.1.1), appropriate link purposes (WCAG 2.4.4), and text alternativesfor non-text content (WCAG 1.1.1).

Systems and methods are thus needed which overcome the limitations ofprior art assistive technologies. Various features and characteristicswill also become apparent from the subsequent detailed description andthe appended claims, taken in conjunction with the accompanying drawingsand this background section.

SUMMARY

Various embodiments of the present invention relate to systems andmethods for, inter alia: i) crawling and scanning websites to detectcompliance issues relating to web accessibility best practices andstandards (which may include but are not limited to WCAG); ii) providinga developer portal for manually fixing compliance issues, includingaccess to libraries of preconfigured blocks of example remediation code;iii) programmatically fixing compliance issues and otherwise enhancingthe user experience for people with diverse abilities, in particularaging populations and individuals who have vision, hearing, motor, andintellectual disabilities, including those who are color blind,dyslexic, learning to read, and looking to maintain focus, ormulti-task; iv) remediating and enhancing websites and other userinterfaces by injecting JavaScript (or similarly functioning code) atthe website server, where the JavaScript is configured to manipulate theweb page DOM to provide an enhanced, customizable user experience forindividuals with disabilities; v) providing a modular suite of assistivetechnologies which may be independently or concurrently enabled,including a player module for converting text to audible speech, areader module for manipulating font, contrast, and other visualattributes and for presenting a consistent, simplified and universallydesigned site and menu layout structure, a voice function to allow theuser to interact with the content using voice commands, and a pageelements menu module which allows a user to navigate through elements,including but not limited to headings, by dynamically inserting andextracting tab indices which function as page anchors; vi) using asecondary device to control a primary device in the context of assistivetechnologies; vii) selectively parsing a web page or other content tomore efficiently perform text-to-speech conversion; viii) providing newor overriding existing alternative (alt) text, based on heuristics whichmay include known file paths and hyperlinks; ix) using artificialintelligence (AI) to provide alternative text for photographs, graphics,and videos and to provide audio descriptions of video content; x)periodically checking remediated code to determine if the remediationremains valid; xi) seamlessly integrating culturally appropriate voicefonts into text-to-speech (TTS) conversions based on contextual languagetags; xii) using audio sprites to enhance TTS conversion for structureddata; and xiii) persisting user interface preferences across diversedomains.

It should be noted that the various inventions described herein, whileillustrated in the context of websites and stand-alone kiosks, are notso limited. Those skilled in the art will appreciate that the systemsand methods described herein may contemplate any paradigm in whichassistive technologies may be brought to bear to enhance the userexperience for individuals with disabilities.

Moreover, while various embodiments are described as using AEJavaScript, it is understood that any approach which augments existingcode to remediate compliance issues and integrate assistive technologiesto enhance the user experience for individuals with disabilities iscontemplated by the inventions described herein.

Various other embodiments, aspects, and features are described ingreater detail below.

BRIEF DESCRIPTION OF THE DRAWINGS

Exemplary embodiments will hereinafter be described in conjunction withthe following drawing figures, wherein like numerals denote likeelements, and:

FIG. 1 is a schematic flow diagram of a web crawler process for scanningwebsites in accordance with various embodiments;

FIG. 2 is a schematic flow diagram of an exemplary process for real-timeauto-detection and audio enablement (RADAE) of page content and elementtypes in accordance with various embodiments;

FIG. 3 is a schematic flow diagram illustrating the operation of a pageelements menu module in accordance with various embodiments;

FIG. 4 is a schematic flow diagram illustrating an exemplary process forinserting and deleting tab indices in accordance with variousembodiments;

FIG. 5 is a schematic flow diagram illustrating an exemplary remediationdelivery process in accordance with various embodiments;

FIG. 6 is a schematic flow diagram illustrating an exemplary smart textlookup process in accordance with various embodiments;

FIG. 7 is a schematic flow diagram illustrating an exemplary smart imagedescription process in accordance with various embodiments;

FIG. 8 is a schematic flow diagram illustrating an exemplary smart videodescription process in accordance with various embodiments;

FIG. 9 is a schematic flow diagram illustrating the operation of anexemplary TTS process with multi-layer caching in accordance withvarious embodiments;

FIG. 10 is a schematic flow diagram illustrating the operation of anexemplary voice module (e.g., AEVoice) in accordance with variousembodiments;

FIG. 11 is a schematic flow diagram illustrating the operation of anexemplary language translation module employing selective voice font inaccordance with various embodiments;

FIG. 12 is a combined schematic block and schematic flow sequencediagram illustrating an exemplary apparatus and method for rendering anAE JavaScript enhanced web page or other user interface in accordancewith various embodiments; and

FIG. 13 is a schematic block diagram and flow sequence diagramillustrating the use of a secondary device to control a primary devicein accordance with various embodiments.

DETAILED DESCRIPTION

The following detailed description of the invention is merely exemplaryin nature and is not intended to limit the invention or the applicationand uses of the invention. Furthermore, there is no intention to bebound by any theory presented in the preceding background or thefollowing detailed description.

Various embodiments of the present invention relate to systems andmethods for bringing websites and other user interfaces into compliancewith prevailing standards for accessibility by persons withdisabilities. In various embodiments, this is accomplished by scanningthe website and programmatically detecting issues in a robust andefficient manner, and injecting code into the HTML document object model(DOM) to facilitate both programmatically and manually remediating theissues, as described in greater detail below.

More particularly, web pages and other electronic documents accessibleonline (or otherwise accessible through a graphical user interface(GUI)) typically have an established reading order embodied in the DOM,including visual elements that are tagged with alternative textdescriptions. The nodes of the document are organized in a treestructure, called the DOM tree. When an HTML page is rendered, thebrowser downloads the HTML into local memory and automatically parses itbefore displaying the page.

The W3C Document Object Model (DOM), a W3C (World Wide Web Consortium)standard for accessing documents, is a platform and language-neutralinterface that allows programs and scripts (such as JavaScript) todynamically access and update the content, structure, and style of adocument. The HTML DOM is a standard object model and programminginterface for HTML, and defines the properties of all HTML elements andthe methods to access the HTML elements. In other words, the HTML DOM isa standard for how to get, change, add, delete, or otherwise interactwith HTML elements.

In the context of the present invention, objects in the DOM tree may beaddressed and manipulated by an integrated JavaScript code baseavailable from AudioEye, Inc. (AE) at www.audioeye.com, sometimesreferred to herein as the AE JavaScript. The AE JavaScript createsclient-side interactivity with the objects in the DOM tree.

When an end-user accesses a website enabled with the techniquesdescribed herein, a version of the AE JavaScript is one of thecomponents that loads on that page. When loaded, the JavaScript injectsappropriate compliance fixes into the page. Conventional screen readers(such as JAWS, NVDA, or Voice Over) read and process the page,leveraging various compliance remediation techniques applied to thepage. Specifically, the AE JavaScript checks for specificnon-conformance issues and, if detected, programmatically fixes them.

In various embodiments, the AE JavaScript enhances the user experienceusing a series of secure communication links with cloud-based webservices, in conjunction with various browser techniques. For example, areal-time auto-detection and audio enablement (RADAE) engine detectspage content and element types. Through cascading style sheet (CSS)selector identification and techniques similar to x-path, the AEJavaScript recognizes individual HTML entities based on their placementwithin the DOM and their tag or other identifier. The AE JavaScriptreorganizes the DOM elements into a strategically organized layout andthen applies rules for enabling accessibility. In an embodiment, onlypage markup is altered, not the underlying content. In this way, theoriginal version of the website remains unaltered when viewed withoutassistive technologies.

As the user requests page content, real-time TTS (text-to-speech) audiois generated through a secure, encrypted link with cloud-based services.Corresponding audio may be played back to the user using native browserfunctionality (e.g., a standard HTML5 audio player).

In an embodiment, the AE JavaScript may be placed in the global include(such as the footer include—just before the closing </body> tag). Onceapplied globally, a Call-to-Action icon may be appropriately displayed,for example in the bottom right hand corner of each page.

In a further embodiment, a website scan performed in accordance with thetechniques described below provides publishers with access to compliancereports and remediation controls, allowing the publisher full controlover their level of compliance without having to manipulate source code.This access may also include detailed analytics outlining the trafficdetails and user behaviors, including a log of communications associatedwith a Help Desk function to facilitate continuous site improvement.

In accordance with one aspect of the present invention, the systemcrawls (spiders) the website and gathers the pages to be analyzed in aninitial evaluation phase. In this regard, various scanning parametersincluding maximum crawl time and level of recursion (sometimes referredto as page depth) may be configurable.

The system then pulls in each URL (page) and evaluates it for WCAG orsimilar compliance issues. For each identified compliance issue, thesystem either programmatically fixes the issue (also referred to hereinas auto-remediation) or alerts a human to do so. For programmatic aswell as manual fixes, the system may utilize one or more code blocksfrom one or more remediation libraries, for example in a dynamic linklibrary (DLL), JavaScript object notation (JSON) format, database, orother structured storage mechanism.

The system suitably implements manual and programmatic remediations byfirst acquiring remediation code during the AE JavaScript loadingprocess, and then applying appropriate remediation code to the renderedcontent. Remediation code may be acquired as part of the AE JavaScript'sinitial payload, from a specific URL, or from the AE hostinginfrastructure. Remediations immediately manipulate the DOM, causing thecorrections and enhancements to take effect at the time the content hasfinished loading and rendering. Keyboard users are able to use standardkeys such as tab to navigate through the remediated page, regardless ofwhether or not a screen reader or other AT is being utilized, reapingthe benefits of the applied DOM manipulations. For users that do not usea stand-alone or native screen reader, the AE JavaScript embodies aplayer function which may be configured to read the remediated pagealoud, as described in greater detail below.

FIG. 1 is a schematic flow diagram of a crawler or “spider” process 100capable of generating a list of URLs to be included as part of aninitial compliance assessment (scan) of a website, in accordance withvarious embodiments. In particular, the crawler process 100 utilizes aconfiguration file to determine the depth of the scan (typicallyexpressed in terms of page depth or levels of recursion), the maximumrun time, and the starting URL. The starting URL is then added as thefirst element to a page stack (memory) 101.

With continued reference to FIG. 1, when the AE JavaScript commences theinitial scanning phase, the process 100 reaches out to a bridge 102 thatspawns a headless browser session (i.e. PhantomJS) 103. Successive URLsare then retrieved and rendered by a link extraction process 104, whichdetects all links within the rendered DOM and adds unique URLs to thestack 101. The process 100 retrieves successive URLs from the stack andcontinues crawling until the site is fully cataloged, timeout isreached, or page depth has been exhausted.

After the crawler or “spider” process completes, the scanning processinitiates. The scanning process ingests a set of pages, which may bemanually configured, attained via the foregoing crawl/spider process ora variant thereof, or from previous scans. Once ingested, the scanningprocess iterates through each unique URL, loading the page in a headlessbrowser, applying the AE JavaScript, executing a series of tests, andultimately delivering the results of the scan back to another process,system, or storage medium.

Once the website is scanned and initial fixes implemented (through theinclusion of the AudioEye JavaScript), site developers may access adevelopment portal and attend to manual fixes, as discussed in greaterdetail below. Concurrently, users may access the remediated site andenjoy the resulting enhanced user experience even before manualremediation is complete.

More particularly and referring now to FIG. 2, the AE JavaScript may beconfigured to call a RADAE process 200 to initiate real-timeauto-detection and audio enablement of page content. The process 200loads a configuration file (e.g., JSON, XML) to identify the point atwhich content processing begins. Metadata 201 (e.g., JSON configurationmetadata) surrounding the starting node 202 is passed back to thecalling process. The process 200 may then request the next or previousitem 203.

With continued reference to FIG. 2, a heuristics engine 204 determineswhich element should be presented back based on various factorsincluding, inter alia: whether the node contains text; whether the nodeis visible; the relative position of the node on the DOM. Users mayrequest the RADAE to move forward or backward through valid elementsusing the heuristics engine 204. Programmatic (e.g., AE JavaScript) 206or user initiated 205 changes to the DOM cause the RADAE 200 toreevaluate the next or previous element contextually, using theheuristic engine 204.

Referring now to FIG. 12, a combined schematic block and schematic flowsequence diagram 1200 illustrates an exemplary apparatus and method forrendering a web page or other AE JavaScript enhanced user interface inaccordance with various embodiments.

More particularly, the system includes a user device 1201 suitablyequipped with a web browser 1202, a first server 1205 configured to hosta website 1204 enhanced with an integrated AE JavaScript code base 1206,and a second server 1208 configured to host various processes andservices accessible by the first server including a RADAE or analogouslyfunctional module 1210 and a TTS module 1212.

In accordance with various embodiments, the browser requests a web page(Task 1214) from the first server, whereupon the AE JavaScript retrievesthe RADAE module (Task 1216) from the second server 1208 and returns theRADAE module to the user device 1201 for execution by the web browser1202 (Task 1218). The first server also sends the HTML page andreorganized DOM to the browser (Task 1220). The browser then requestsany additional resources (Task 1222), whereupon the AE JavaScriptreturns remediated page mark-up (Task 1224) and the remediated page isrendered.

With continued reference to FIG. 12, when the browser requests pagecontent (Task 1226), such as a text-to-audio conversion, the AEJavaScript 1206 running in the local browser requests audio from thesecond server 120 (Task 1228), and the audio is passed directly back tothe browser 1202 for playback to the user (Task 1230).

In an embodiment, the AE JavaScript facilitates a modular implementationof various ATs, including an audio player function, a screen reader toolsuite (e.g., font, magnification, contrast), a voice command feature,and a page elements menu.

In accordance with another aspect of the invention, user preferences maybe persisted across a plurality of domains enabled with the AEJavaScript. In particular, the AE JavaScript may be configured to placea cookie into the browser using an invisible iframe, so that when a userswitches domains to another AE enabled site which also has an invisibleiframe, the browser is informed that the previous AT preferences havebeen re-enabled for the new domain, thereby seamlessly enabling the ATfunctions and preferences (embedded in the browser cookie) acrossmultiple domains without any additional user action. As a result, eachtime a user starts a new session on an AE JavaScript enabled site, theprevious preferences are automatically invoked.

In accordance with a further aspect of the invention, the AE JavaScriptmay be configured to inject a branding icon (e.g., the AudioEye bursticon) into an enabled website (e.g., at the bottom right corner),suitably superimposing a timed toggle over the universal accessibilityicon and using CSS and/or JavaScript to animate the image. A distinctiveaudible tone may also be played on the first or every visit to anenabled site as a further branding strategy. These are the visual andaudio indicators to the user that the AE JavaScript is loaded andremediations have been applied. Hovering/Clicking on the burst revealsthe AudioEye Ally+™ tool bar, which may include controls forindependently enabling the player, the reader, the help desk, and anyother desired functions.

In the context of the present invention, the “call to action” refers towhen and how the system toggles from standard site interaction withoutthe AE JavaScript enabled, to site interaction with the AE JavaScriptenabled. Low vision keyboard users may tab thru or use keyboardshortcuts to navigate from link to link, with or without a screenreader, until they get to the enabling icon. Mouse users can mouse clickdirectly on the enabling icon to reveal the tool bar and/or initiate theplayer module. Alternatively, AE JavaScript enabled websites allow theuser to press the space bar (or other predetermined key or keycombination) to reveal the enabling icon; pressing the escape keyterminates execution of any active AE tool. In a further embodiment,pressing an alternative key or key combination (e.g., Alt+Shift+SpaceBar) opens the AT tool bar but suppresses the audible player. This is aconsequence of the modular approach contemplated by the presentinvention, as described in greater detail below.

More particularly, the AE JavaScript suitably implements a modularapproach to a suite of assistive technologies, including graphicalcontrols, and audible player, voice (microphone) control, and a pageelements menu module. Each module is independent yet stackable upon theother modules. Prior art screen readers, on the other hand, tie thegraphic controls to the audio component; that is, prior art systemshighlight text as it is reads aloud, such that the only way to highlighttext without also hearing it is to manually pause the audio componentafter enabling the visual component.

Once the AE JavaScript is enabled, the user may select the “Skip tomain” option which allows keyboard users to drive focus to the maincontent within the web page, as suggested by WCAG best practices.Thereafter, the user may tab (or other trigger such as Ctrl R) to revealthe page elements menu which allows keyboard users to jump to contentusing any combination of at least the following page element menus:landmark navigation, page headings, hyperlinks, images, and the like.This can be done using the modular approach of the present inventioneither with the player (screen reader) function enabled, or silently fortab users who want to jump around the page. In contrast, prior art pageelement menus (or rotors) are only available if the audible screenreader is engaged.

FIG. 3 is a schematic flow diagram illustrating the operation of a pageelements menu module 300 according to the present invention. Inparticular, the page items menu module 300 may be configured to parsethe DOM 301 to identify elements which are focusable or are of a certaintype (e.g., <p>), while filtering out elements that are unable to bespoken. The full element list may be passed to an element classifiers302 which classifies the elements based on the user actions that can beperformed on them (e.g., elements which can be clicked on and followedsuch as a link, elements which can be filled in such as a form field,text which can be read aloud, and the like). Markup is then generated303 and passed on for display 304.

With continued reference to FIG. 3, the markup 303 visuallydifferentiates between content that is currently visible within theviewport, and content that requires scrolling to reveal. In view of theforegoing distinction between visible and non-visible items, changes tothe viewport preferably initiate the markup generation process 303 toupdate the Page Items Menu to reflect the currently visible elements305.

When using the Page Elements Menu without engaging the audio player,when an element is selected the AE JavaScript dynamically inserts atabindex element attribute to anchor the page at the selected object(footer, top of page, link, etc.). When the user thereafter focuses awayfrom the selected element, the AE JavaScript dynamically extracts thetabindex (“anchor”). In this way, referred to herein as ad hoc pagenavigation, traditionally non-navigable items become navigable as aresult of the insertion of temporary tags (when the Page Elements Menuis enabled) and subsequent deletion of the temporary tags when the PageElements Menu is disabled. The tags may be inserted/extractedindividually when each page element is selected using the Page ElementsMenu; alternatively, the tags may be inserted/extracted or en masse whenthe Page Elements Menu is engaged/disengaged.

FIG. 4 is a schematic flow diagram illustrating an exemplary process ofinserting and deleting tab indices. In particular, a user may select anitem from a Page Elements Menu 400. The system inspects 401 the menu'starget associated with the selection to determine if the user could usethe tab key to advance through the content and land on their selection.If the selected item cannot be navigated to using the tab key, a process402 injects some form of a tabbable markup (e.g., HREF/anchor/tabindex)into the selected item. A process 403 then sets the browser focus to theselected element. Once the user moves from or de-selects 404 the item, asubsequent process 405 removes any injected markup; otherwise, nochanges to the DOM are made.

Various remediation techniques such as improving the DOM throughattribute (e.g., alt text) tagging will now be described.

FIG. 5 is a schematic flow diagram illustrating an exemplary remediationdelivery process. In particular, once the AE JavaScript loads 500,manual remediations present in the configuration are applied andexecuted 501. A process 502 then runs to scan the page to detectcompliance issues. Using a heuristics engine 503, detected complianceissues are mapped to pre-existing remediation scripts 504. A process 505then programmatically executes/applies each matched remediation. Datareturned from this process may include issues that existed prior toremediation, issues resolved through individual scripts, and the levelof confidence that each remediation was successful in resolving thecompliance issue.

With reference to FIG. 7, for images lacking an adequate alt text thesystem may be configured to programmatically send the image to an imagerecognition server to determine the nature of the image and insert abest fit alt text. By way of non-limiting example, the system may beconfigured to dynamically insert the phrase “president Obama” or “GeorgeClooney” based on information returned from the image recognitionserver, in lieu of the missing or default alt text (e.g., “image”). Thedynamically inserted text can then be spoken to the user, either using anative screen reader or the AE Player.

FIG. 7 is a schematic flow diagram illustrating an exemplary smart imagedescription process. In particular, an image 700 is passed to a smartimage description system 701. A process 702 then sends the image one ormore internal and/or external image recognition systems 703, to obtainone or more interpretations of the image. Image descriptions may then bereturned either through a heuristics engine 704 or a natural languageengine 705 to generate a human readable, preferably grammaticallycorrect version of the image description, which is then returned 706 tothe calling process.

Referring now to FIG. 6, another auto-remediation feature of the presentinvention involves Smart Text Replacement. By way of non-limitingexample, CNN, Fox News, Bank of America, and other sites often sharesimilar “Like us on Facebook” and “Follow us on Twitter” elements, whichmay include tracking pixels to count clicks. As a screen reader userencounters these elements, processing them can be cumbersome if they arenot labeled and tagged properly. The AE JavaScript may be configured toidentify common file paths with hyperlinks (e.g. a hyperlink to aFacebook “like us” landing page), and programmatically assign bestpractice descriptive alt text to the element based on the filepath/hyperlink. In this way, when a screen reader or the AE playerencounters the element, it is properly and consistently vocalized as“like us on Facebook” even if the element is not coded that way.

FIG. 6 is a schematic flow diagram illustrating an exemplary smart textlookup process 600. In particular, the process 600 may be configured tosearch the DOM for commonly occurring elements (e.g., Facebook Like Us,advertisements, App Store links) that do not have text descriptions orhave ambiguous text descriptions. An element classification process 601suitably employs a heuristic engine 602 to identify relevant attributes(e.g., H REF) to empower process 603 to apply text description tags tothe un-tagged or improperly tagged element.

The foregoing techniques may be extended to facilitate the programmaticgeneration of audio description of a video file, for example usingartificial intelligence (AI). In one embodiment, a video may be sent toa server which samples the frames and identifies respective images, andusing AI techniques returns text which describes the subject matter ofthe video file based on similarities and/or differences between/amongrespective (e.g., successive) frames. The text which is generated isanalogous to subtitles displayed during a sporting event. Note that theAI derived description of the video is different from, and can besuperimposed onto (or in synchronized conjunction with), the audio trackwhich may accompany the video in the ordinary course.

FIG. 8 is a schematic flow diagram illustrating an exemplary smart audiodescription process. In particular, the calling process provides a video800 to the smart audio description module 801. Each video frame (or asampling thereof) is passed to a process 802 which sends the images toone or more internal and/or external image recognition systems 803, tothereby obtain a single or multiple interpretations of each image.Sequential differences 806 between successive images may be used toinfer the subject matter of the video, and thus a high level descriptionof the video. A heuristic engine 804 or natural language engine 805generates a TTS convertible text description which is returned 807 tothe calling process, along with metadata such as per frame time stampsfor use in synchronizing the description with the video track.

Yet a further feature of the present invention involves auto-remediationof manually fillable form fields. By way of non-limiting example, inorder for a screen reader (or the AE player) to determine that the formis requesting the user to enter the user's first name, the developermust code the form label (analogous to a picture's alt text) to indicatethat the user is being prompted to enter his or her first name. If thefield is not properly labeled, confusion may ensue.

In accordance with an embodiment, the AE JavaScript may be configured toprogrammatically inspect nearby text elements and infer and inject anappropriate label based on contextual cues such as the words “name,”“first,” and “last” as well as relative positions and types ofattributes, i.e., a SPAN tag in front of an INPUT field.

As discussed above, the AE JavaScript may be used to refine thedescription of an image using a developer portal, whereupon the new alttext is saved and injected into the DOM via AE JavaScript when the pagerenders. In accordance with a further aspect of the invention, thesystem may be configured to periodically ping the page containing theremediated alt text to determine if the image is still there and, ifnot, extract or modify the remediation accordingly. If the imagechanges, the system may be configured to trigger a prompt to reevaluatethe alt text for the new image, and either change or suppress thepreviously remediated text. The foregoing technique may be extendedbeyond images to periodically assess the validity of any remediationover time.

In an embodiment, a developer portal implements a live remediatorfunction which is maintained at a different server from the websitebeing remediated. The developer portal allows the page being assessed tobe launched and displayed within an iFrame available from the developerportal or, alternatively, within a separate browser tab or windowoutside of the developer portal. Generally analogous to the industrystandard web accessibility evaluation (WAVE) tool available athttp://wave.webaim.org, the developer portal of the present inventionembodies a browser plug-in for assessing WCAG-type compliance of webpages, and displays issues detected during the evaluation phasediscussed above.

In an alternative embodiment, the developer portal allows the developerto write the markup while simultaneously viewing the rendered remediatedpage in real time thru an iFrame from the same developer portal, withouthaving to separately access the underlying website outside of thedeveloper portal.

As discussed above, once the AE audio player is engaged, the AEJavaScript sends blocks of text from the underlying website server to atext-to-speech (TTS) module at a remote AE server, which returns anaudio file to the website server or directly to the end user device inreal-time (or near real-time). In this context, the audio player maycomprise AE JavaScript code which instructs the native audio driver onthe device to stream audio to the user. The logic for determiningkeyboard focus and, hence, to determine where to start the TTS, residesin the AE JavaScript.

In one embodiment, the AE JavaScript may be configured to send apredetermined block of words (e.g., 500 words) at a time or oneparagraph, whichever is smaller. The system sends the next paragraphwhen the audio player is nearly finished speaking the current paragraph.In addition, the system only sends text blocks (e.g., paragraphs) forTTS conversion which are proximate the cursor focus, as opposed to theentire page. This is in contrast to prior art systems which typicallysend the whole page when the screen reader is engaged.

FIG. 9 is a schematic flow diagram illustrating the operation of anexemplary TTS process with multi-layer caching. In particular, TTSrequests 900 may originate from the audio player embedded in the AEJavaScript or from another calling function. Each TTS request firstpasses through a text normalization process 901 which removes whitespace and other noise. A hash may then be generated 902 based on thesubmitted text, language tag, and desired voice font. The normalizedrequest may optionally be sent to a content delivery network (CDN) 903that first checks a CDN cache 904; if not found, the request is sent toan asset server 905. The asset server performs its own cache check 906;if not found, a new audio file is requested from the TTSprocess/API/provider 907.

With continued reference to FIG. 9, those skilled in the art willappreciate that prior art CDN cache systems typically rely on full URLmatches, so that if a user visits site1.com and makes a TTS request forthe string “Hello,” and thereafter makes the same request at site2.com,prior art CDN systems will create and hold two copies of the same TTSconversion audio file. In contrast, the present asset cache 906 onlyneeds to maintain one copy, inasmuch as it is based on, for example, therequested text block and voice font (and not the full URL). In this way,only a single request needs to be made to the TTS process for the sametext, even across multiple domains.

Presently known voice applications include Apple's Siri™, Nuance'sDragon™, Windows' Cortana™, and Amazon's Alexa™ which simply drive auser to a web page in response to a voice request; that is, they convertspeech to text, apply the text to a database or look-up table, andreturn a web page or search results for display and loading. The presentsystem, on the other hand, operates inside the web page and interactswith the objects and elements in the page via the DOM to fill out forms,apply for a job, purchase products, and otherwise navigate within andinteract with the website, kiosk, or non-web based environment.Moreover, as described in greater detail below, stacking the AEVoicefunction onto the AE audio player facilitates apparent bi-synchronousoral navigation and execution.

FIG. 10 is a schematic flow diagram illustrating the operation of anexemplary voice module, sometimes referred to herein as AEVoice, inaccordance with the present invention. In particular, the AEVoice modulemoo may be embedded in the AE JavaScript at the website server. The AEJavaScript may be configured to load an iFrame 1001 which links the pageto a secure AE URL at a remote server. This iFrame 1001 may beconfigured to open a WebSocket connection to an AEVoice server 1002.When active, voice data captured via the user's microphone 1003 isstreamed to the AEVoice module 1002 via the WebSocket connection inblocks or chunks.

In one embodiment, voice data may be captured by automatic speechrecognition (ASR) software native to the device and supported throughthe browser application in use, in which case, text is generated locally(from the user's device), thus bypassing the AEVoice WebSocket listenerconnection and allowing the user to interact with the elements of theweb page (DOM) without relying on an ASR API connection with AudioEye.

Once silence is detected or other suitable metrics indicate the end of avoice chunk by the iFrame 1001, a complete audio file built from thestreamed audio is sent to a speech-to-text or ASR API 1004. Textreturned from the API 1004 is passed back to the iFrame 1001 for furtherprocessing and analysis. The iFrame code may present the user with theirspoken text, perform actions or execute processes based on the voicecommand, or the like.

In accordance with a further aspect of the present invention, theAEVoice module and the AE audio player functions may be configured toallow users to engage bi-directionally with websites, speaking commandswhile listening to web content.

In one embodiment, users can manipulate a visual icon or keyboardshortcut to engage the AEVoice module and its listening capabilities. Ifthe AE audio player is playing content when the user engages themicrophone, the audio content may be paused. Normal AEVoice flowproceeds, with audio streamed to the AEVoice service and text returnedonly after the user stops speaking (or the icon/keyboard shortcut ispressed a second time). If a command is detected, it will be executed;if not, playback of the page content may resume.

In another embodiment, rather than engaging the visual icon or keyboardshort cut as described above, the user may engage the voice function bypressing and holding the icon or shortcut, much like using aPush-to-Talk device.

In yet another alternative mode intended for users with headsets, theAEVoice software may be configured to always listen, regardless ofwhether the audio player is outputting audio. The AEVoice system maythen make calibration decisions based on detected audio levels, tothereby ascertain when the user is speaking and only sending speech tothe AEVoice module when it is determined that the user is speaking.

In accordance with a further aspect of the invention, the AE audioplayer may render seamless language transitions based on language tagsencountered during web page or other document navigation. For example,when the AE player reading content aloud in English encounters a blockof text accompanied by a different language tag (e.g., Spanish), theplayer may be configured to dynamically and programmatically read thetagged element in the appropriate language (Spanish in this example),and also employ a corresponding Spanish voice font. That is, the AEJavaScript sends the text block to the TTS engine (at a remote server)along with the language tag, and returns an audio file in theappropriate language and voice font. This concept may be extended sothat contextual Help is also spoken based on the then current languagetag.

In this regard, those skilled in the art will appreciate that a voicefont is a computer-generated voice that can be controlled by specifyingparameters such as speed, pitch, and inflexion and made to pronouncetext input. The concept is analogous to a text font in that the sameinput may be represented in several different ways based on the designof each font.

FIG. 11 is a schematic flow diagram illustrating the operation of anexemplary language translation module employing selective voice font. Inparticular, requests made from the AE audio player module 1100 to a CDN1101 or assets system 1102 may include a language attribute. Whenpresent, the assets system 1102 may be configured to utilize an API 1103to identify the source text language and, if the source and destinationlanguages are different, utilize an API 1104 to translate from onelanguage to another. The assets system 1102 may then select anappropriate voice font icon the destination language and in theappropriate gender (e.g., the user's gender) and return back translatedaudio.

In accordance with a further aspect of the present invention, the AEJavaScript may be configured to allow full navigation through the webpage hierarchy using only voice commands.

In this regard, presently known systems for using voice to control acomputer are limited, and are not well suited for website and menunavigation. For example, Amazon's Echo™ is a hands free, voicecontrolled speaker which can connect to Alexa™ voice, the brains behindEcho. However, Echo has no keyboard, and no screen, making it difficultif not impossible for use with web page navigation. Although a usercould potentially configure presently known voice command systems toorder products, those systems do not lend themselves to interacting witha web page in real time to do so. In contrast, the AE JavaScript allowsinteraction using only the native capabilities of the browser, and usingthe inherent navigation of the existing web page content as it iscurrently laid out in the DOM. In this sense, any website configuredwith the AE JavaScript may be fully controlled and accessed inconjunction with common supported and native ASR software applicationssuch as Siri on iOS.

By way of further illustration, presently known voice command systemscan interact with a native application (such as the Direct TVapplication) to control the application (for example, changing thechannel) in response to a voice command. In contrast, the presentinvention facilitates interacting with content in an existing web pagehierarchy using only voice commands.

Specifically, when a web page enabled with AE JavaScript expects theuser to enter text, the AE JavaScript injects code allowing voice totext conversion, so that when the user speaks, the speech is convertedto text in real-time and the corresponding text inserted into the textbox or form field on the web page.

Those skilled in the art will appreciate that voice detection istypically a native browser function which must be enabled in thebrowser. By way of example, when a user visits a first website andenables voice, the AE JavaScript may be configured to drop a cookie intothe browser using an invisible iFrame, so that when the user switchesdomains to another AE enabled which also has an invisible iframe, thebrowser is able to detect the presence of a prior authorization for theiFrame and re-enable voice controls for the current domain, with theresult that the voice function remains seamlessly enabled across domainswithout any user action needed. This is because the AE JavaScript looksthru the iframe to find the “permission to use voice” which is embeddedin the browser cookie. More generally, browser preferences (e.g.,contrast, font size, magnification, reader visualization functionenabled) may, thus, be persisted across AE JavaScript enabled domains bydropping cookies in this manner. As a result, each time a user starts anAE experience, the user may do so using the previous preferences.

In accordance with a further aspect of the present invention, processingefficiencies may be obtained by concatenating a plurality of audio bitesinto a single audio file, referred to herein as an audio sprite. Byanalogy, an image sprite is a collection of several images displayedfrom a single graphics file (e.g., jpeg), using CSS to define whichsub-images appear in which regions of the 2 dimensional space in whichthe jpeg is rendered. The analogous audio sprite is a small TTS file(e.g., an alphabet/numeric/common name.WAV file), sent from the AEserver to the local machine to perform local TTS on text entered by theuser into a field such as a form field, search box, or whenever enteredtext is read back to the user character-by-character. The audio spritemay employ CSS to define which numbers or letters are spoken atparticular timed intervals as the audio is rendered (spoken).

The foregoing aspects of the present invention may be extended tocontemplate a secondary device configured to control the primary deviceon which the website, menu, or other user interface is rendered. Withregard to voice commands, the speech to text conversion may occur at thewebsite server, at a remote server, within the primary device whileleveraging local ASR resources that may or may not rely on their ownremote resources, or on a secondary device such as a mobile device,personal digital assistant, or wearable device (e.g., Fitbit, jawbone,watch, key fob, lanyard, or the like). Device pairing may beaccomplished in any desired manner, such as any of the techniquesdiscussed in U.S. Pat. No. 8,903,978 B2 entitled “Method and Apparatusfor Pairing a Mobile Device to an Output Device” issued Dec. 2, 2014,the entire contents of which are hereby incorporated herein by thisreference.

The secondary device can be configured to control a primary device(e.g., website, airport kiosk, drive up menu, hotel room remote control)which is enabled for voice commands as described above, but which maynot have a microphone that is convenient for the user (or none at all).Moreover, many individuals prefer not to touch the primary screen, butare comfortable swiping and otherwise interacting with their ownpersonal (secondary) device screen to control the primary screen.

By way of non-limiting example, presently known soda dispensing machinesand other menu driven interfaces allow users to pair a secondarypersonal device to the soda machine, and thereby control the operationof the machine using the personal device. In an embodiment, thisparadigm may be extended to allow the user to enter voice commands intothe personal (secondary) device, and thereby control the primary device(e.g., soda machine, drive up or walk up menu or kiosk) using voicecommands, touch screen interaction, gestures, and the like.

FIG. 13 is a schematic block diagram and flow sequence diagramillustrating the use of a secondary device to control a primary deviceaccording to various embodiments.

More particularly, the system includes a secondary device 1302 (e.g., amobile telephone or wearable device) suitably equipped with input/output(IO) capability such as a microphone 1301, a touch screen 1305, a hapticmodule 1305, and/or a speaker 1307. The system further includes aprimary device 1304 such as a product dispensing machine, menu,information kiosk, computer, help desk, or the like, a primary deviceserver 1310 configured to host the interface on the primary device whichis suitably enhanced within an integrated AE JavaScript code base, and asecond server 1312 configured to host various processes and servicesaccessible by the first server including RADAE and/or TTS services.

In an embodiment, the secondary device requests pairing with the primarydevice (Task 1230), which confirms the paired arrangement (Task 1322).The user may then interact with the primary device, for example byrequesting content (e.g., TTS) (Task 1324), whereupon the primary devicepasses the request to the primary server (Task 1326), which may beco-located with the primary device. The primary server then accesses anaccelerator at the AE server (Task 1328). The AE server 1312 thenreturns the remediated content to the secondary device (Task 1330),either directly or via the primary device and/or the primary server.

With continued reference to FIG. 13, the user requests an object (Task1332) such as a menu item, a form field, or the like, whereupon theprimary server selects and returns the object to the secondary device(Task 1334). The user may request that voice commands be enabled (Task1336), whereupon the AE server acknowledges that voice is enabled (Task1338). The user speaks a voice command into the secondary device (Task1440) triggering a speech-to-text conversion which may be processed atthe secondary device, the primary device, or the AE server, and aconverted text file returned to the primary and/or secondary device(Task 1342). The system then processes the voice command as text (Task1344), and responds to the command (Task 1346) by taking the requestedaction (e.g., executing the voice command).

More generally, the principals and techniques discussed herein may beemployed to allow an individual with a disability to effectively reachoutside his or her personal circle, using a personal (secondary) deviceto control or otherwise interact with kiosks, menus, websites, remotecontrollers, televisions, vehicles, and virtually any other systememploying assistive technologies.

By way of non-limiting example, presently known fast food, product,ticket, and cash (ATM) dispensing, and information kiosks are not wellequipped to accommodate visually impaired, low vision, wheel chairbound, or other users who are unable, unwilling, or who simply choosenot to interact directly with the primary device (a menu kiosk in thisexample). By stacking or otherwise integrating some form of the AEJavaScript on the operating system, server, or other control moduleassociated with the primary device, and by pairing or linking theprimary and secondary devices together, the user may interact with thekiosk using the personal device.

In particular, the AE JavaScript may be configured to enable the primarydevice to speak menu choices aloud to the user, whereupon the user maynavigate or otherwise interact with the primary device by speaking intoor swiping/touching a touch screen on the secondary device. In a menucontext, for example, the user may be instructed to tap (or speak) thetop left quadrant of the screen to select sandwiches, the top right forfries, the bottom left for drinks, the bottom right for more options,and double tap anywhere to exit or return to the previous navigationallevel. By interacting with the secondary device in a way which mimicsthe primary device, the assistive technologies embodied in the secondarydevice may be manifested in the secondary device, effectively extendingthe reach of individuals with disabilities to all device platforms.

A method is thus provided for persisting a user preference associatedwith an assistive technology across multiple web domains. The methodincludes: installing remediation code on a first server hosting a firstwebsite and on a second server hosting a second website; establishing,using a browser operating on a user device, a first session with thefirst website; enabling an assistive technology during the firstsession; defining a user preference associated with the assistivetechnology during the first session; placing, by the remediation code, acookie into the browser indicating the first user preference;establishing, using the browser operating on the user device, a secondsession with the second website; and using the cookie to persist theuser preference to the second session.

In an embodiment, placing the cookie into the browser comprises passingthe cookie through an iframe, where the iframe may comprise an invisibleiframe.

In an embodiment, persisting the user preference to the second sessionis controlled by the remediation code without any additional useraction.

In an embodiment, the remediation code comprises JavaScript.

In an embodiment, the first server is remote from the second server.

In an embodiment, the assistive technology comprises one of: an audioplayer function; a screen reader tool suite; a voice command feature;and a page elements menu.

In an embodiment, the screen reader tool suite comprises font,magnification, and contrast controls.

In an embodiment, the user preference comprises maintaining theassistive technology in the enabled state.

In an embodiment, the method further includes embedding indicia of theuser preference in the browser cookie.

Computer code stored in a non-transient medium is also provided forperforming, when executed by a computer processor, the steps of:superimposing a timed toggle of a branding icon over a universalaccessibility icon on a web page; and revealing, in response to a usercommand, an assistive technology tool bar including controls forindependently enabling at least an audio player and a screen reader toolsuite.

In an embodiment, the user command comprises one of hovering over andclicking on the branding icon.

In an embodiment, independently enabling comprises selecting one of: afirst option to enable the audio player without enabling the screenreader tool suite; a second option to enable the screen reader toolsuite without enabling the audio player; and a third option tosimultaneously enable both the audio player and the screen reader toolsuite.

In an embodiment, superimposing the timed toggle comprises using one ofa cascading style sheet (CSS) and JavaScript to periodically animate thebranding icon.

In an embodiment, the assistive technology tool bar further includes acontrol for independently enabling a help desk function.

In an embodiment, wherein the computer code comprises JavaScript.

A method of ad hoc page navigation through a website using a browser isalso provided. The method includes: displaying a page element menucomprising a plurality of objects; in response to the selection of oneof the objects by a user, dynamically inserting an anchor into theobject; displaying the page corresponding to the selected object; and inresponse to the user focusing away from the selected object, dynamicallyextracting the anchor from the object.

In an embodiment, the anchor comprises a tabindex element attribute.

In an embodiment, the plurality of objects comprises at least two of:page heading; hyperlink; image; footer; and top of page.

In an embodiment, displaying the page comprises setting the browserfocus to the selected object.

A method is also provided for programmatically assigning descriptive alttext to an element on web page having an associated document objectmodel (DOM). The method includes: inspecting the DOM for an improperlytagged element having an associated hyperlink; determining the file pathassociated with the hyperlink; and assigning an alt text description tothe improperly tagged element based on the file path.

In an embodiment, the improperly tagged element comprises a user promptto “Like Us on Facebook,” and the file path comprises a link to aFacebook Like Us landing page.

In an embodiment, the improperly tagged element comprises a user promptto “Follow Us on Twitter,” and the file path comprises a link to aTwitter Follow Us landing page.

A method is also provided for programmatically assigning descriptive alttext to an image on web page, the web page having an associated documentobject model (DOM). The method includes: inspecting the DOM for an imagelacking an adequate alt text; sending the image to a remote imagerecognition server to determine the nature of the image; assigning analt text description to the image based on the determined image nature;and speaking the alt text description to a user using an assistivetechnology.

In an embodiment, the assistive technology comprises one of a nativescreen reader and an audio player embedded in JavaScript remediationcode.

In an embodiment, the image recognition server comprises an imagedatabase and a recognition module for comparing the image to thecontents of the image database.

In an embodiment, the nature of the image comprises one of: a landmark;a location; the name of an object; and the name of a person.

A method is also provided for programmatically generating an audiodescription of a video file appearing on web page enhanced withremediation code which includes an embedded audio player. The methodincludes: sending the video file to a remote image recognition server;sampling respective frames of the video file and identifyingcorresponding respective images; using artificial intelligence (AI)techniques to determine the subject matter of the video file based ondifferences between successive frames; returning a text-to-speech (TTS)convertible text file which describes the subject matter of the video;and speaking the text file to a user using the embedded audio player.

In an embodiment, the text file comprises metadata for use insynchronizing the text file with the video file.

In an embodiment, the metadata comprises respective timing dataassociated with each of a plurality of the respective frames.

A method is also provided for enhancing a web page hosted by a firstserver to render the page navigable by low vision users through voicecommands. The method includes: in response to the keyboard selection ofa text element by a user, the text element being of the type whichprompts the user to enter an answer into a field on the web page,generating a text-to-speech (TTS) file corresponding to the textelement; processing the TTS file to thereby audibilize the text elementto the user; capturing a recording of the user speaking the answer;sending the recording to a second server; generating a speech-to-text(STT) file of the recording at the second server; and processing the SITfile at the first server to thereby enter the answer into the field.

In an embodiment, the method further includes establishing a WebSocketconnection between the first and second servers.

In an embodiment, the method further includes suspending audibilizingthe text element to the user while the user is speaking the answer.

In an embodiment, the method further includes resuming audibilizing thetext element to the user when the user is finished speaking the answer.

In an embodiment, the answer comprises a voice command.

In an embodiment, the web page comprises a form and the field comprisesone of a plurality of information fields required to fill out the form.

In an embodiment, the method further includes using an audio sprite tofacilitate audibilizing the answer to the user as the answer is enteredinto the field.

In an embodiment, the audio sprite comprises a CSS to define whichcharacters are audibilized at particular timed intervals.

A method is also provided for controlling a primary device using a handheld device to allow low vision users to access the primary device usingthe hand held device. The method includes: pairing the hand held devicewith the primary device; displaying a menu of elements on the primarydevice; speaking a voice command into the hand held device; sending thevoice command to a remote server to generate a STT file of the voicecommand; and processing the STT file by the primary device to executethe voice command.

As used herein, the word “exemplary” means “serving as an example,instance, or illustration.” Any implementation described herein as“exemplary” is not necessarily to be construed as preferred oradvantageous over other implementations, nor is it intended to beconstrued as a model that must be literally duplicated.

While the foregoing detailed description will provide those skilled inthe art with a convenient road map for implementing various embodimentsof the invention, it should be appreciated that the particularembodiments described above are only examples, and are not intended tolimit the scope, applicability, or configuration of the invention in anyway. To the contrary, various changes may be made in the function andarrangement of elements described without departing from the scope ofthe invention.

What is claimed is:
 1. A remediation web page computer-implemented method of programmatically assigning a descriptive attribute to an untagged element on a web page to enable an audible description of the element, the web page having an associated document object model (DOM), the computer-implemented method comprising: receiving, by a computer system, from a browser of a remote computer via an electronic network, a remediation request associated with a web page, wherein the remediation request comprises a unique identifier associated with the web page, the remediation request generated by a remediation request code operating in the browser; accessing, by the computer system, a remediation code data storage medium based on the unique identifier to determine a remediation code for the web page; retrieving, by the computer system, the determined remediation code for the web page from the remediation code data storage medium; and transmitting, by the computer system, to the browser of the remote computer via the electronic network, the determined remediation code for the web page, wherein the browser uses the determined remediation code to cause the remote computer to process remediation of the web page for displaying the web page on the remote computer, wherein the remote computer operating the browser, based on the determined remediation code, is caused to: detect one or more compliance issues relating to web accessibility standards in code of the web page, wherein at least one of the one or more compliance issues comprises an untagged element, the untagged element comprising an element lacking an adequate descriptive attribute; and apply the determined remediation code to the one or more compliance issues, wherein the determined remediation code comprises at least assigning a descriptive attribute to the untagged element, the descriptive attribute assigned to the untagged element configured to enable an assistive technology to speak the descriptive attribute to a user, wherein the code of the web page comprises at least HTML or the DOM.
 2. The computer-implemented method of claim 1, wherein the unique identifier is a URL address.
 3. The computer-implemented method of claim 1, wherein the determined remediation code assigns an alt text description to the untagged element.
 4. The computer-implemented method of claim 1, wherein the determined remediation code assigns a descriptive HTML attribute to the untagged element in the web page.
 5. The computer-implemented method of claim 1, wherein the determined remediation code is javascript.
 6. The computer-implemented method of claim 1, wherein the remediation request code operating in the browser is javascript.
 7. The computer-implemented method of claim 1, wherein the determined remediation code assigns a title attribute to the untagged element in the web page.
 8. The computer-implemented method of claim 1, wherein the untagged element is an untagged image in the web page.
 9. The computer-implemented method of claim 1, wherein the untagged element is an untagged input field in the web page.
 10. The computer-implemented method of claim 9, wherein the generation of the determined remediation code is based in part on the remote computer analyzing one or more contextual cues in the web page.
 11. The computer-implemented method of claim 1, wherein the causing of the remote computer to process remediation of the web page enables changing the DOM.
 12. The computer-implemented method of claim 1, wherein the causing of the remote computer to process remediation of the web page enables changing HTML for the web page.
 13. The computer-implemented method of claim 1, wherein the determined remediation code is updated by the computer system on a periodic basis.
 14. The computer-implemented method of claim 1, wherein the determined remediation code is generated by executing an artificial intelligence algorithm.
 15. The computer-implemented method of claim 1, wherein the determined remediation code is generated by executing a machine learning algorithm.
 16. A remediation web page computer-implemented method of programmatically assigning a descriptive HTML attribute to an untagged element in a web page to enable an audible description of the untagged element, the web page having an associated document object model (DOM), the computer-implemented method comprising: executing, via a browser operating on a user computer, a remediation request code embedded in the web page; sending, by the user computer, a remediation request over an electronic network to a remote server, wherein the remediation request is for remediating the web page; accessing, by the user computer from the remote server via the electronic network, at least one remediation code for remediating the web page; and executing, by the user computer, the at least one remediation code to cause the user computer to process remediation of the web page to enable an audible description for an untagged element of the web page, wherein the remote server generates the at least one remediation code by: receiving, by the remote server, from the user computer via the electronic network, the remediation request associated with the web page, wherein the remediation request comprises a unique identifier associated with the web page, the remediation request generated by executing the remediation request code operating in the browser; determining, by the remote server, the at least one remediation code for the web page based in part on the unique identifier, wherein the at least one remediation code is stored in a remediation code data storage medium; and causing, by the remote server, transmission via the electronic network to the user computer the at least one remediation code for the web page from the remediation code data storage medium, the at least one remediation code configured to remediate the web page through the browser; the executing, by the user computer, based on the at least one remediation code, further comprises: detecting one or more compliance issues relating to web accessibility standards in code of the web page, wherein at least one of the one or more compliance issues comprises an untagged element, the untagged element comprising an element lacking an adequate descriptive attribute; and applying the at least one remediation code to the one or more compliance issues, wherein the at least one remediation code comprises at least assigning a descriptive attribute to the untagged element, the descriptive attribute assigned to the untagged element configured to enable an assistive technology to speak the descriptive attribute to a user, wherein the code of the web page comprises at least HTML or the DOM.
 17. The computer-implemented method of claim 16, wherein the unique identifier is a URL address.
 18. The computer-implemented method of claim 16, wherein the at least one remediation code assigns an alt text description to the untagged element in the web page.
 19. The computer-implemented method of claim 16, wherein the at least one remediation code assigns a descriptive HTML attribute to the untagged element in the web page.
 20. The computer-implemented method of claim 16, wherein the at least one remediation code is javascript.
 21. The computer-implemented method of claim 16, wherein the remote server comprises one or more computer systems.
 22. The computer-implemented method of claim 16, wherein the at least one remediation code assigns a title attribute to the untagged element in the web page.
 23. The computer-implemented method of claim 16, wherein the untagged element is an untagged image in the web page.
 24. The computer-implemented method of claim 16, wherein the untagged element is an untagged input field in the web page.
 25. The computer-implemented method of claim 24, wherein the generation of the at least one remediation code is based in part on analyzing one or more contextual cues in the web page.
 26. The computer-implemented method of claim 16, wherein the causing of the user computer to process remediation of the web page enables changing the DOM.
 27. The computer-implemented method of claim 16, wherein the causing of the user computer to process remediation of the web page enables changing HTML for the web page.
 28. The computer-implemented method of claim 16, wherein the at least one remediation code is updated by the remote server on a periodic basis.
 29. The computer-implemented method of claim 16, wherein the at least one remediation code is generated by executing an artificial intelligence algorithm.
 30. The computer-implemented method of claim 16, wherein the at least one remediation code is generated by executing a machine learning algorithm. 